How people actually adopt, not just how tools get deployed. Six
components that diagnose the org, earn permission, build skill,
and manufacture momentum — because the program lives or dies
on everything above it.
Components6
ShapeConcentric ripple
OwnershipAI Champions + Lead
PostureEmpathetic, evidence-led
Foxpath™
Change · Six Components · One Adoption CurveDiagnose, enable, amplify, sustain
Six components, on the human side of the program
Reading order: diagnose before you act
Component 01Diagnose
Stakeholder Mapping
What: Map every stakeholder by function, influence, and adoption posture before launch. Identify champions, skeptics, and blockers by name. Re-map quarterly — postures shift as the program produces evidence.
Why: A program that doesn't know who its blockers are will be surprised by them at the worst possible moment. Naming them upfront converts surprises into plans.
By FunctionBy InfluenceBy Posture
Component 02Diagnose
Resistance Profiling
What: Categorize resistance by type: fear of job loss, workflow disruption, distrust of AI outputs, and tool fatigue. Each type gets a specific, named response — not a generic "comms plan."
Why: Treating all resistance as one problem produces one weak intervention. Treating it as four problems produces four sharp ones.
Job LossWorkflowTrustFatigue
Component 03Enable
Training Strategy
What: Role-based, not role-agnostic. End users get workflow-specific training. Champions get methodology — scoring, discovery, facilitation. Execs get ROI literacy and the failure modes to watch for.
Why: A single training track is built for nobody. Three tracks, each short and specific, beats one long course that everyone tunes out of.
End UsersChampionsExecs
Component 04Enable
Psychological Safety
What:Explicit, named permission to experiment and fail at the crawl stage. Failed pilots are reviewed as data, not as performance issues. The Lead and Sponsor publicly own this — without that air cover, the permission isn't real.
Why: Punishing early AI mistakes kills adoption faster than any technical barrier. Safety is the precondition for the experimentation the rest of the framework depends on.
PermissionAir CoverNo Blame
Component 05Amplify
Wins Amplification
What: Every measurable win — hours saved, cost reduced, process accelerated — is documented, quantified against the pre-deployment baseline, and socialized through the channels the org already reads. No win goes unsignalled.
Why: Momentum is not found, it's manufactured. A program that ships quietly is a program nobody else volunteers to join.
DocumentQuantifySocialize
Component 06Sustain
Adoption Curve
What: Sequence rollouts deliberately along the curve. Early adopters get tools first, generate visible wins, and create pull from the majority. Laggards are addressed last, with evidence — not first, with persuasion.
Why: Trying to convert skeptics before you have wins is the most common adoption failure. The curve only bends when the early end is already bent.
Early AdoptersMajorityLaggards Last
Change ownership
Who runs what
AI Champions
Run change in the BU. Own stakeholder maps, surface resistance, broadcast wins to peers.
AI Transformation Lead
Owns the change strategy across BUs. Resources training. Holds the air cover for psychological safety.
Executive Sponsor
Publicly signs the safety contract. Amplifies wins at the top. Reframes failed pilots as learning, not waste.
"The four pillars above this one decide what gets built. Change Management decides whether anyone uses it."